…crash

Add an ErrorBoundary and wrap each answer item in it, so a failure in one
section degrades only that section instead of blanking the whole message.
Also guard the optional streamable chain in StandardResourceCard that could
throw on a null value and take down the message.

Plan mode is only meaningful inside the instance/device editor for now,
so gate the composer toggle on immersive mode and force the persisted
planMode off whenever the user is outside immersive (including on load),
preventing a stale value from being sent in non-immersive contexts.

- Guard the optional streamable chain in FlowResourceCard directly instead
  of relying on a render boundary to mask the throw. Reduce ErrorBoundary to
  a single last-resort backstop per answer item in AiMessage; drop the
  per-section boundary wrappers in AnswerWrapper.
- Rewrite QuestionsList on top of the existing ff-radio-group (single-select)
  and ff-checkbox (multi-select) components so options look like standard,
  clickable form controls and stay consistent with the rest of the app.
- Replace the imperative growComposerToContent DOM measuring with CSS
  field-sizing on the textarea; drop the manual reflows and the auto-grown
  flag. The composer auto-sizes to content and pins to an explicit height
  only after a drag-resize.

…-replies

handleMessageResponse lived in the composer's send handler, so a reply to a
query sent from the questions card was fetched but never rendered over HTTP
(without comms-beta the reply only renders via the MQTT push handler). Fold
the response handling into handleQuery so every entry point (composer and the
question/plan cards) renders the reply without re-implementing it.

…mode

# Conflicts:
#	frontend/src/components/expert/components/ExpertChatInput.vue
#	frontend/src/components/expert/components/messages/components/AnswerWrapper.vue
#	frontend/src/stores/context.js
#	frontend/src/stores/product-expert.js

- Remove the unused contextOverrides param threaded through handleQuery/sendQuery.
- Stop persisting planMode so approving a plan (which turns it off) no longer
  wipes the user's preference; it defaults off per session.
- Replace the planChangeRequest/composerReset counters with a single
  composerCommand consumed and cleared like pendingInput, collapsing two
  composer watchers into one.
- Give the composer textarea min-height: 0 so a long plan loaded via Edit
  manually scrolls instead of overflowing the chat.
- Add a size="small" variant to the shared ff-toggle-switch and drop the
  fragile :deep sizing overrides. The prop defaults to "normal" (an inert
  class) so existing consumers are unchanged.
- Trim verbose comments across the plan-mode files.

The min-height: 0 needed for the composer to scroll instead of grow was
only on the textarea, not its flex parent. Add it to .input-wrapper so the
whole flex chain can shrink and a long plan loaded via Edit scrolls within
the capped composer.

…mode

# Conflicts:
#	frontend/src/stores/context.js